Named entity recognition visual context and caption data

ABSTRACT

A caption of a multimodal message (e.g., social media post) can be identified as a named entity using an entity recognition system. The entity recognition system can use a visual attention based mechanism to generate a visual context representation from an image and caption. The system can use the visual context representation to identify one or more terms of the caption as a named entity.

CLAIM FOR PRIORITY

This application claims the benefit of priority to U.S. Application Ser. No. 62/610,051, filed Dec. 22, 2017, which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

Embodiments of the present disclosure relate generally to machine learning and, more particularly, but not by way of limitation, to identifying named entities using machine learning.

BACKGROUND

Named Entity Recognition (NER) is a computational task in which one or more words of text are determined to be a named entity (e.g., a noun, celebrity, city, organization). For example, an NER scheme may assume a pop song exists called “Modern Baseball”. Given a sentence “I love modern baseball!” as an input, a NER model attempts to determine whether one or more terms of the sentence are a named entity, e.g., whether the sentence is expression of love for the sport baseball in modern times or a pop song with a title of “Modern Baseball”. Typically, an NER scheme needs a large well-structured dataset from which it can train a model, which can then be applied to recognize one or more words as a named entity. However, recognizing a named entity from a few words, some of which may be intentionally misspelled (e.g., “I luv new yoooooork ctiy!”) is difficult for current NER schemes.

BRIEF DESCRIPTION OF THE DRAWINGS

To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure (“FIG.”) number in which that element or act is first introduced.

FIG. 1 is a block diagram showing an example messaging system for exchanging data (e.g., messages and associated content) over a network.

FIG. 2 is block diagram illustrating further details regarding a messaging system having an integrated virtual object machine learning system, according to example embodiments.

FIG. 3 is a schematic diagram illustrating data that may be stored in a database of a messaging server system, according to certain example embodiments.

FIG. 4 is a schematic diagram illustrating a structure of a message, according to some embodiments, generated by a messaging client application for communication.

FIG. 5 is a schematic diagram illustrating an example access-limiting process, in terms of which access to content (e.g., an ephemeral message, and associated multimedia payload of data) or a content collection (e.g., an ephemeral message story) may be time-limited (e.g., made ephemeral).

FIG. 6 shows internal functional components of a visual gazetteer named entity system, according to some example embodiments.

FIG. 7A shows a flow diagram of a method for identifying named entities in a caption of a multimodal message using visual attention based image data and gazetteer data, according to some example embodiments.

FIG. 7B shows a flow diagram of method of identifying named entities using a visual attention mechanism, according to some example embodiments.

FIG. 8 shows an architecture for generating named entity recognition tags using visual attention word-based data and gazetteer vectors, according to some example embodiments.

FIG. 9 shows an example architecture of the gazetteer engine, according to some example embodiments.

FIG. 10 shows an architecture for a lexical generator, according to some example embodiments.

FIG. 11 shows an example architecture of the classification engine, according to some example embodiments.

FIG. 12 shows an architecture for the visual word engine and the classification engine, according to some example embodiments.

FIG. 13A shows an image of the multimodal message, according to some example embodiments.

FIG. 13B shows an example image that corresponds to the image with certain areas being highlighted according to the caption.

FIG. 14A shows an example multimodal message, according to some example embodiments.

FIG. 14B shows example overlay content that has been identified using named entity recognition, according to some example embodiments.

FIG. 15 is a block diagram illustrating a representative software architecture, which may be used in conjunction with various hardware architectures herein described.

FIG. 16 is a block diagram illustrating components of a machine, according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative embodiments of the disclosure. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide an understanding of various embodiments of the inventive subject matter. It will be evident, however, to those skilled in the art, that embodiments of the inventive subject matter may be practiced without these specific details. In general, well-known instruction instances, protocols, structures, and techniques are not necessarily shown in detail.

As discussed, named entity recognition is a difficult computational task. Further, performing NER using social media posts is made more difficult due to the shortness of the captions, intentional misspelling of words, acronyms, and emojis being used in a certain way based on societal trends. To this end, a visual named entity system can be implemented to identify named entities in multimodal captions using a visual attention network and vector information from words and characters in a caption. In some example embodiments, an image of a multimodal message is processed via an attention network to indicate which portions of the region are more relevant to a caption that accompanies the image. The attention network can generate a visual context vector from the image and the caption which can be integrated into a recurrent neural network (e.g., a bidirectional long short term memory (LSTM) having conditional random field layer), which can indicate which terms in the caption correspond to a named entity. The identified named entity can be used to select and incorporate content for inclusion in a social media post. For example, the visual named entity system can determine that a certain band is being discussed in a caption and suggest a guitar emoji for inclusion or overlay in a social media post.

FIG. 1 is a block diagram showing an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple client devices 102, each of which hosts a number of applications including a messaging client application 104. Each messaging client application 104 is communicatively coupled to other instances of the messaging client application 104 and a messaging server system 108 via a network 106 (e.g., the Internet).

Accordingly, each messaging client application 104 is able to communicate and exchange data with another messaging client application 104 and with the messaging server system 108 via the network 106. The data exchanged between messaging client applications 104, and between a messaging client application 104 and the messaging server system 108, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video, or other multimedia data).

The messaging server system 108 provides server-side functionality via the network 106 to a particular messaging client application 104. While certain functions of the messaging system 100 are described herein as being performed by either a messaging client application 104 or by the messaging server system 108, it will be appreciated that the location of certain functionality within either the messaging client application 104 or the messaging server system 108 is a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the messaging server system 108, and to later migrate this technology and functionality to the messaging client application 104 where a client device 102 has a sufficient processing capacity.

The messaging server system 108 supports various services and operations that are provided to the messaging client application 104. Such operations include transmitting data to, receiving data from, and processing data generated by the messaging client application 104. This data may include message content, client device information, geolocation information, media annotation and overlays, message content persistence conditions, social network information, and live event information, as examples. Data exchanges within the messaging system 100 are invoked and controlled through functions available via user interfaces (UIs) of the messaging client application 104.

Turning now specifically to the messaging server system 108, an application programming interface (API) server 110 is coupled to, and provides a programmatic interface to, an application server 112. The application server 112 is communicatively coupled to a database server 118, which facilitates access to a database 120 in which is stored data associated with messages processed by the application server 112.

The API server 110 receives and transmits message data (e.g., commands and message payloads) between the client devices 102 and the application server 112. Specifically, the API server 110 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client application 104 in order to invoke functionality of the application server 112. The API server 110 exposes various functions supported by the application server 112, including account registration; login functionality; the sending of messages, via the application server 112, from a particular messaging client application 104 to another messaging client application 104; the sending of media files (e.g., images or video) from a messaging client application 104 to a messaging server application 114 for possible access by another messaging client application 104; the setting of a collection of media data (e.g., a story); the retrieval of such collections; the retrieval of a list of friends of a user of a client device 102; the retrieval of messages and content; the adding and deletion of friends to and from a social graph; the location of friends within the social graph; and opening application events (e.g., relating to the messaging client application 104).

The application server 112 hosts a number of applications and subsystems, including the messaging server application 114, an image processing system 116, and a social network system 122. The messaging server application 114 implements a number of message-processing technologies and functions particularly related to the aggregation and other processing of content (e.g., textual and multimedia content) included in messages received from multiple instances of the messaging client application 104. As will be described in further detail, the text and media content from multiple sources may be aggregated into collections of content (e.g., called stories or galleries). These collections are then made available, by the messaging server application 114, to the messaging client application 104. Other processor- and memory-intensive processing of data may also be performed server-side by the messaging server application 114, in view of the hardware requirements for such processing.

The application server 112 also includes the image processing system 116, which is dedicated to performing various image processing operations, typically with respect to images or video received within the payload of a message at the messaging server application 114.

The social network system 122 supports various social networking functions and services, and makes these functions and services available to the messaging server application 114. To this end, the social network system 122 maintains and accesses an entity graph (e.g., entity graph 304 in FIG. 3) within the database 120. Examples of functions and services supported by the social network system 122 include the identification of other users of the messaging system 100 with whom a particular user has relationships or whom the particular user is “following,” and also the identification of other entities and interests of a particular user.

The application server 112 is communicatively coupled to a database server 118, which facilitates access to a database 120 in which is stored data associated with messages processed by the messaging server application 114.

FIG. 2 is block diagram illustrating further details regarding the messaging system 100, according to example embodiments. Specifically, the messaging system 100 is shown to comprise the messaging client application 104 and the application server 112, which in turn embody a number of subsystems, namely an ephemeral timer system 202, a collection management system 204, an annotation system 206.

The ephemeral timer system 202 is responsible for enforcing the temporary access to content permitted by the messaging client application 104 and the messaging server application 114. To this end, the ephemeral timer system 202 incorporates a number of timers that, based on duration and display parameters associated with a message or collection of messages (e.g., an Ephemeral Message Story), selectively display and enable access to messages and associated content via the messaging client application 104. Further details regarding the operation of the ephemeral timer system 202 are provided below.

The collection management system 204 is responsible for managing collections of media (e.g., collections of text, image, video, and audio data). In some examples, a collection of content (e.g., messages, including images, video, text, and audio) may be organized into an “event gallery” or an “event story.” Such a collection may be made available for a specified time period, such as the duration of an event to which the content relates. For example, content relating to a music concert may be made available as a “story” for the duration of that music concert. The collection management system 204 may also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client application 104.

The collection management system 204 furthermore includes a curation interface 208 that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface 208 enables an event organizer to curate a collection of content relating to a specific event (e.g., delete inappropriate content or redundant messages). Additionally, the collection management system 204 employs machine vision (or image recognition technology) and content rules to automatically curate a content collection. In certain embodiments, compensation may be paid to a user for inclusion of user-generated content into a collection. In such cases, the curation interface 208 operates to automatically make payments to such users for the use of their content.

The annotation system 206 provides various functions that enable a user to annotate or otherwise modify or edit media content associated with a message. For example, the annotation system 206 provides functions related to the generation and publishing of media overlays for messages processed by the messaging system 100. The annotation system 206 operatively supplies a media overlay (e.g., a geofilter or filter) to the messaging client application 104 based on a geolocation of the client device 102. In another example, the annotation system 206 operatively supplies a media overlay to the messaging client application 104 based on other information, such as social network information of the user of the client device 102. A media overlay may include audio and visual content and visual effects. Examples of audio and visual content include pictures, text, logos, animations, and sound effects. An example of a visual effect includes color overlaying. The audio and visual content or the visual effects can be applied to a media content item (e.g., a photo) at the client device 102. For example, the media overlay includes text that can be overlaid on top of a photograph generated by the client device 102. In another example, the media overlay includes an identification of a location (e.g., Venice Beach), a name of a live event, or a name of a merchant (e.g., Beach Coffee House). In another example, the annotation system 206 uses the geolocation of the client device 102 to identify a media overlay that includes the name of a merchant at the geolocation of the client device 102. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in the database 120 and accessed through the database server 118.

In one example embodiment, the annotation system 206 provides a user-based publication platform that enables users to select a geolocation on a map and upload content associated with the selected geolocation. The user may also specify circumstances under which particular content should be offered to other users. The annotation system 206 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

In another example embodiment, the annotation system 206 provides a merchant-based publication platform that enables merchants to select a particular media overlay associated with a geolocation via a bidding process. For example, the annotation system 206 associates the media overlay of a highest-bidding merchant with a corresponding geolocation for a predefined amount of time.

The visual named entity recognition system 210 comprises one or more neural networks configured to identify an entity referenced by a multimodal message, as discussed in further detail below. In some example embodiments, the visual named entity recognition system 210 is integrated and run from the application server 112.

FIG. 3 is a schematic diagram illustrating data 300 which may be stored in the database 120 of the messaging server system 108, according to certain example embodiments. While the content of the database 120 is shown to comprise a number of tables, it will be appreciated that the data could be stored in other types of data structures (e.g., as an object-oriented database).

The database 120 includes message data stored within a message table 314. An entity table 302 stores entity data, including an entity graph 304. Entities for which records are maintained within the entity table 302 may include individuals, corporate entities, organizations, objects, places, events, and so forth. Regardless of type, any entity regarding which the messaging server system 108 stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).

The entity graph 304 furthermore stores information regarding relationships and associations between or among entities. Such relationships may be social, professional (e.g., work at a common corporation or organization), interest-based, or activity-based, for example.

The database 120 also stores annotation data, in the example form of filters, in an annotation table 312. Filters for which data is stored within the annotation table 312 are associated with and applied to videos (for which data is stored in a video table 310) and/or images (for which data is stored in an image table 308). Filters, in one example, are overlays that are displayed as overlaid on an image or video during presentation to a recipient user. Filters may be of various types, including user-selected filters from a gallery of filters presented to a sending user by the messaging client application 104 when the sending user is composing a message. Other types of filters include geolocation filters (also known as geo-filters), which may be presented to a sending user based on geographic location. For example, geolocation filters specific to a neighborhood or special location may be presented within a user interface by the messaging client application 104, based on geolocation information determined by a Global Positioning System (GPS) unit of the client device 102. Another type of filter is a data filter, which may be selectively presented to a sending user by the messaging client application 104, based on other inputs or information gathered by the client device 102 during the message creation process. Examples of data filters include a current temperature at a specific location, a current speed at which a sending user is traveling, a battery life for a client device 102, or the current time.

Other annotation data that may be stored within the image table 308 is so-called “lens” data. A “lens” may be a real-time special effect and sound that may be added to an image or a video.

As mentioned above, the video table 310 stores video data which, in one embodiment, is associated with messages for which records are maintained within the message table 314. Similarly, the image table 308 stores image data associated with messages for which message data is stored in the message table 314. The entity table 302 may associate various annotations from the annotation table 312 with various images and videos stored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages and associated image, video, or audio data, which are compiled into a collection (e.g., a story or a gallery). The creation of a particular collection may be initiated by a particular user (e.g., each user for whom a record is maintained in the entity table 302). A user may create a “personal story” in the form of a collection of content that has been created and sent/broadcast by that user. To this end, the user interface of the messaging client application 104 may include an icon that is user-selectable to enable a sending user to add specific content to his or her personalstory.

A collection may also constitute a “live story,” which is a collection of content from multiple users that is created manually, automatically, or using a combination of manual and automatic techniques. For example, a “live story” may constitute a curated stream of user-submitted content from various locations and events. Users whose client devices 102 have location services enabled and are at a common location or event at a particular time may, for example, be presented with an option, via a user interface of the messaging client application 104, to contribute content to a particular live story. The live story may be identified to the user by the messaging client application 104 based on his or her location. The end result is a “live story” told from a community perspective.

A further type of content collection is known as a “location story,” which enables a user whose client device 102 is located within a specific geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some embodiments, a contribution to a location story may require a second degree of authentication to verify that the end user belongs to a specific organization or other entity (e.g., is a student on the university campus).

FIG. 4 is a schematic diagram illustrating a structure of a message 400, according to some embodiments, generated by a messaging client application 104 for communication to a further messaging client application 104 or the messaging server application 114. The content of a particular message 400 is used to populate the message table 314 stored within the database 120, accessible by the messaging server application 114. Similarly, the content of a message 400 is stored in memory as “in-transit” or “in-flight” data of the client device 102 or the application server 112. The message 400 is shown to include the following components:

-   -   A message identifier 402: a unique identifier that identifies         the message 400.     -   A message text payload 404: text, to be generated by a user via         a user interface of the client device 102, and that is included         in the message 400.     -   A message image payload 406: image data captured by a camera         component of a client device 102 or retrieved from memory of a         client device 102, and that is included in the message 400.     -   A message video payload 408: video data captured by a camera         component or retrieved from a memory component of the client         device 102, and that is included in the message 400.     -   A message audio payload 410: audio data captured by a microphone         or retrieved from the memory component of the client device 102,         and that is included in the message 400.     -   Message annotations 412: annotation data (e.g., filters,         stickers, or other enhancements) that represents annotations to         be applied to the message image payload 406, message video         payload 408, or message audio payload 410 of the message 400.     -   A message duration parameter 414: a parameter value indicating,         in seconds, the amount of time for which content of the message         400 (e.g., the message image payload 406, message video payload         408, and message audio payload 410) is to be presented or made         accessible to a user via the messaging client application 104.     -   A message geolocation parameter 416: geolocation data (e.g.,         latitudinal and longitudinal coordinates) associated with the         content payload of the message 400. Multiple message geolocation         parameter 416 values may be included in the payload, with each         of these parameter values being associated with respective         content items included in the content (e.g., a specific image in         the message image payload 406, or a specific video in the         message video payload 408).     -   A message story identifier 418: identifies values identifying         one or more content collections (e.g., “stories”) with which a         particular content item in the message image payload 406 of the         message 400 is associated. For example, multiple images within         the message image payload 406 may each be associated with         multiple content collections using identifier values.     -   A message tag 420: one or more tags, each of which is indicative         of the subject matter of content included in the message         payload. For example, where a particular image included in the         message image payload 406 depicts an animal (e.g., a lion), a         tag value may be included within the message tag 420 that is         indicative of the relevant animal. Tag values may be generated         manually, based on user input, or may be automatically generated         using, for example, image recognition.     -   A message sender identifier 422: an identifier (e.g., a         messaging system identifier, email address, or device         identifier) indicative of a user of the client device 102 on         which the message 400 was generated and from which the message         400 was sent.     -   A message receiver identifier 424: an identifier (e.g., a         messaging system identifier, email address, or device         identifier) indicative of a user of the client device 102 to         which the message 400 is addressed.

The contents (e.g., values) of the various components of the message 400 may be pointers to locations in tables within which content data values are stored. For example, an image value in the message image payload 406 may be a pointer to (or address of) a location within the image table 308. Similarly, values within the message video payload 408 may point to data stored within the video table 310, values stored within the message annotations 412 may point to data stored in the annotation table 312, values stored within the message story identifier 418 may point to data stored in the story table 306, and values stored within the message sender identifier 422 and the message receiver identifier 424 may point to user records stored within the entity table 302.

FIG. 5 is a schematic diagram illustrating an access-limiting process 500, in terms of which access to content (e.g., an ephemeral message 502, and associated multimedia payload of data) or a content collection (e.g., an ephemeral message story 504) may be time-limited (e.g., made ephemeral).

An ephemeral message 502 is shown to be associated with a message duration parameter 506, the value of which determines an amount of time that the ephemeral message 502 will be displayed to a receiving user of the ephemeral message 502 by the messaging client application 104. In one embodiment, where the messaging client application 104 is an application client, an ephemeral message 502 is viewable by a receiving user for up to a maximum of 10 seconds, depending on the amount of time that the sending user specifies using the message duration parameter 506.

The message duration parameter 506 and the message receiver identifier 424 are shown to be inputs to a message timer 512, which is responsible for determining the amount of time that the ephemeral message 502 is shown to a particular receiving user identified by the message receiver identifier 424. In particular, the ephemeral message 502 will only be shown to the relevant receiving user for a time period determined by the value of the message duration parameter 506. The message timer 512 is shown to provide output to a more generalized ephemeral timer system 202, which is responsible for the overall timing of display of content (e.g., an ephemeral message 502) to a receiving user.

The ephemeral message 502 is shown in FIG. 5 to be included within an ephemeral message story 504 (e.g., a personal story, or an event story). The ephemeral message story 504 has an associated story duration parameter 508, a value of which determines a time duration for which the ephemeral message story 504 is presented and accessible to users of the messaging system 100. The story duration parameter 508, for example, may be the duration of a music concert, where the ephemeral message story 504 is a collection of content pertaining to that concert. Alternatively, a user (either the owning user or a curator user) may specify the value for the story duration parameter 508 when performing the setup and creation of the ephemeral message story 504.

Additionally, each ephemeral message 502 within the ephemeral message story 504 has an associated story participation parameter 510, a value of which determines the duration of time for which the ephemeral message 502 will be accessible within the context of the ephemeral message story 504. Accordingly, a particular ephemeral message 502 may “expire” and become inaccessible within the context of the ephemeral message story 504, prior to the ephemeral message story 504 itself expiring in terms of the story duration parameter 508. The story duration parameter 508, story participation parameter 510, and message receiver identifier 424 each provide input to a story timer 514, which operationally determines whether a particular ephemeral message 502 of the ephemeral message story 504 will be displayed to a particular receiving user and, if so, for how long. Note that the ephemeral message story 504 is also aware of the identity of the particular receiving user as a result of the message receiver identifier 424.

Accordingly, the story timer 514 operationally controls the overall lifespan of an associated ephemeral message story 504, as well as an individual ephemeral message 502 included in the ephemeral message story 504. In one embodiment, each and every ephemeral message 502 within the ephemeral message story 504 remains viewable and accessible for a time period specified by the story duration parameter 508. In a further embodiment, a certain ephemeral message 502 may expire, within the context of the ephemeral message story 504, based on a story participation parameter 510. Note that a message duration parameter 506 may still determine the duration of time for which a particular ephemeral message 502 is displayed to a receiving user, even within the context of the ephemeral message story 504. Accordingly, the message duration parameter 506 determines the duration of time that a particular ephemeral message 502 is displayed to a receiving user, regardless of whether the receiving user is viewing that ephemeral message 502 inside or outside the context of an ephemeral message story 504.

The ephemeral timer system 202 may furthermore operationally remove a particular ephemeral message 502 from the ephemeral message story 504 based on a determination that it has exceeded an associated story participation parameter 510. For example, when a sending user has established a story participation parameter 510 of 24 hours from posting, the ephemeral timer system 202 will remove the relevant ephemeral message 502 from the ephemeral message story 504 after the specified 24 hours. The ephemeral timer system 202 also operates to remove an ephemeral message story 504 either when the story participation parameter 510 for each and every ephemeral message 502 within the ephemeral message story 504 has expired, or when the ephemeral message story 504 itself has expired in terms of the story duration parameter 508.

In certain use cases, a creator of a particular ephemeral message story 504 may specify an indefinite story duration parameter 508. In this case, the expiration of the story participation parameter 510 for the last remaining ephemeral message 502 within the ephemeral message story 504 will determine when the ephemeral message story 504 itself expires. In this case, a new ephemeral message 502, added to the ephemeral message story 504, with a new story participation parameter 510, effectively extends the life of an ephemeral message story 504 to equal the value of the story participation parameter 510.

In response to the ephemeral timer system 202 determining that an ephemeral message story 504 has expired (e.g., is no longer accessible), the ephemeral timer system 202 communicates with the messaging system 100 (e.g., specifically, the messaging client application 104) to cause an indicium (e.g., an icon) associated with the relevant ephemeral message story 504 to no longer be displayed within a user interface of the messaging client application 104. Similarly, when the ephemeral timer system 202 determines that the message duration parameter 506 for a particular ephemeral message 502 has expired, the ephemeral timer system 202 causes the messaging client application 104 to no longer display an indicium (e.g., an icon or textual identification) associated with the ephemeral message 502.

FIG. 6 shows internal functional components of a visual named entity system 210, according to some example embodiments. As illustrated, the visual named entity recognition system 210 comprises an interface engine 605, a word engine 610, a part-of-speech engine 615, a character engine 620, a gazetteer engine 625, a visual word engine 630, a combination engine 635, a classification engine 640, and a message engine 645. The interface engine 605 manages identification or otherwise generation of one or more images using an image capture device (e.g. a camera) of the client device. The interface engine 605 may also identify or generate a multimodal message that has one or more images (e.g. an image, a video sequence), audio data captured simultaneously with the one or more images by the client device, and a caption input by the user of the client device. The word engine 610 is a neural network configured to generate word embeddings, according to some example embodiments. The part-of-speech engine 615 is configured to receive one or more words (e.g. a sentence) and label each of the words using a part of speech tag. For example, the part-of-speech engine 615 may label one word as a noun, another word is a preposition, and yet another word as a verb, and so on. The character engine 620 is a neural network configured to generate character embeddings from one or more words (e.g. words in the caption of the multimodal message identified or otherwise generated by the interface engine 605). The gazetteer engine 625 is configured to generate gazetteer vectors for each of the words in the caption of the multimodal message. A gazetteer is a list of words of a particular type, such as a list of celebrities, a list of places, a list of organizations, a list of sports teams, and so on. In some example embodiments, one or more words of the caption in the multimodal message are identified as corresponding to a gazetteer vector and the message is tagged with the gazetteer tag. Each gazetteer tag has a corresponding gazetteer vector in a gazetteer tag lookup table. In some example embodiments, the gazetteer tag lookup table comprises eight vectors which corresponds to eight gazetteer's. In some example embodiments, each word can be used to generate up to eight gazetteer vectors from the lookup table. For the given word, each of the vectors can be concatenated to represent that word's final gazetteer feature vector.

The visual word engine 630 is configured to generate a word vector from an image and caption of the multimodal message. In particular, and as explained in further detail below, the image can be processed using a convolution on neural network and the caption can be processed using a bidirectional recurrent neural network. The bidirectional recurrent neural network can generate a vector that can be used to call attention to or otherwise emphasize certain regions of the image that more strongly correspond to nouns and verbs in the caption. The combination engine 635 is configured to generate a combined vector that, for a given word in the caption, concatenates the part-of-speech representation for that word, the word embedding for that word, the gazetteer representation for that word, a forward time LSTM character embedding, and backward time LSTM character embedding.

The classification engine 640 is configured to receive the combined vector generated by the combination engine 635 and the visual word vector generated by the visual word engine 630, and recursively generate an indication whether the words in the caption correspond to a named entity. The message engine 645 is configured to select overlay content that has been pre-associated with an identified named entity in the caption, and overlay the overlay content on the multimodal message. The message engine 645 can also manage publishing the multimodal message with the overlay content as an ephemeral message on a social network site.

FIG. 7A shows a flow diagram of a method 700 for identifying named entities in a caption of a multimodal message using visual attention based image data and gazetteer data, according to some example embodiments. At operation 705, the interface engine 605 generates the multimodal message. For example, the interface engine 605 may use a camera of the client device 102 to capture video, and an audio sensor of the client device 102 to simultaneously capture voice data and may further receive a caption input by the user of the client device 102 for inclusion with the audio data and the video data in the multimodal message.

At operation 710, the gazetteer engine 625 analyzes each word in the caption of the multimodal message and generates a gazetteer vector for the words in the caption that correspond to gazetteer's (e.g. lists of celebrities, lists of cities, and so on). At operation 715, the character engine 620 generates character vectors from each character in the caption of the multimodal message. At operation 720, the visual word engine 630 generates a visual word vector from the image of the multimodal message and the caption of the multimodal message, as discussed in further detail below with reference to FIG. 12.

At operation 725, the classification engine 640 labels one or more words in the caption of the multimodal message as a named entity. At operation 730, the message engine 645 identifies content pre-associated with the identified entity. At operation 735, the message engine 645 generates an ephemeral message from the associated content and the multimodal message. For example, the message engine 645 may overlay the pre-associated content on the multimodal message to generate the ephemeral message. At operation 740, the message engine 645 publishes the ephemeral message on a network site, such as a social media website or a network service that provides the ephemeral message is to one or more client devices via the messaging client application 104.

FIG. 7B shows a flow diagram of a method 750 for identifying a named entity without gazetteer, according to some example embodiments. In the example of FIG. 7B, entities are named using the visual word engine 630 (e.g., architecture 1200 of FIG. 12) without the user of lists or gazetteers. At operation 755, the interface engine 605 generates the multimodal message. For example, the interface engine 605 may use a camera of the client device 102 to capture video, and an audio sensor of the client device 102 to simultaneously capture voice data and may further receive a caption input by the user of the client device 102 for inclusion with the audio data and the video data in the multimodal message.

At operation 760, the visual word engine 630 generates a visual context vector using the caption and the image. For example, the caption is encoded as a query using a LSTM, and visual representations (e.g., global and/or regional representation) are generated using a convolutional neural network. The query and the visual representations are input into an attention neural network which then generates the visual context vector (e.g., as discussed in further detail below with reference to FIG. 12).

At operation 760, the visual word engine 630 integrates the visual context vector into an entity recognition neural network. The entity recognition neural network comprises a bidirectional LSTM layer, a conditional random field layer, and, optionally, a modulated gate layer, according to some example embodiments. In some example embodiments, the visual context vector is used to seed or initialize a forward LSTM cell of the entity recognition neural network. In some example embodiments, the visual context vector is integrated at the word-level (e.g., for each word of the caption) using the modulated gate layer, as discussed in further detail below, with reference to FIG. 12.

At operation 770, the classification engine 640 labels one or more words in the caption of the multimodal message as a named entity. At operation 775, the message engine 645 identifies content pre-associated with the identified entity. As used here, pre-associated means after the neural network is trained but before the network model is distributed to client devices; that is, pre-associated means before run time by an end user of client device 102. At operation 780, the message engine 645 generates an ephemeral message from the associated content and the multimodal message. For example, the message engine 645 may overlay the pre-associated content on the multimodal message to generate the ephemeral message. At operation 785, the message engine 645 publishes the ephemeral message on a network site, such as a social media website or a network service that provides the ephemeral message is to one or more client devices via the messaging client application 104.

Although the operations of method 750 are discussed as separate steps, it is appreciated by those having ordinary skill in the art of neural networks that some of the operations (e.g., operations 760, 765, 770) are performed as one step by a neural network architecture (e.g., architecture 1200) which is trained via end-to-end training.

FIG. 8 shows an architecture 800 for generating named entity recognition tags using visual attention word-based data and gazetteer vectors, according to some example embodiments. As illustrated, a multimodal message 805 is input into a lexical generator 810. The lexical generator, can comprise the word engine 610, the part-of-speech engine 615, the gazetteer engine 625, the character engine 620, and a combination engine 635. Details of how the lexical generator 810 connection outputs data between the engines is detailed in the following figures. At a high-level, the combination engine 635 combines vectors from the word engine 610, the part-of-speech engine 615, the gazetteer engine 625, and the character engine 620 to generate a combined vector which is input into the classification engine 640. The multimodal message 805 is further input into a visual word engine 630, which is configured to generate a word vector from the image and the caption of the multimodal message 805, as discussed in further detail below with reference to FIG. 12. The classification engine 640 receives the input data from the visual word engine 630 and the lexical generator 810 and recurrently generates (e.g. using a bidirectional LSTM neural network) tags indicating whether one or more of the words in the caption of the multimodal message is a named entity. For example, as illustrated, the classification engine 640 can generate output data 815. For example, if the multimodal message included the caption “Florence and the machine surprise patient with private concert in Austin!”, the output data 815 may indicate that the term “Florence” is the beginning of a name and the term machine is the end of a name of an entity using a type of tag or metadata (as indicated by the bold font). Further the output data 815 may also indicate that the term Austin is likely the city of Austin, Tex. and not a name for example using it further tag or metadata (as indicated by the underlined font).

FIG. 9 shows an example architecture 900 of the gazetteer engine 625, according to some example embodiments. In FIG. 9, the caption in the multimodal message is “Cristiano Rinaldo scores 3 in Portugal win”. The gazetteer engine 625 can generate a matrix 905 which tags each word of the caption as corresponding to a gazetteer of a plurality of gazetteers used to train the gazetteer engine 625. In particular, for example, the term Cristiano is labeled as a beginning tag of a gazetteer and Rinaldo is labeled as the ending tag of a gazetteer of a same entity. Portugal is further labeled as belonging to a location-based gazetteer. The gazetteer engine 625 consults a lookup table 910, which stores gazetteer vectors 915 for each of the possible gazetteers and associates each word in the caption with the is proper gazetteer vector if that term in the caption is to receive a gazetteer vector (e.g. the term in may be a null vector).

FIG. 10 shows an architecture 1000 for the lexical generator 810, according to some example embodiments. As illustrated, each character of the caption can be input into the character engine 620 which incorporates a bidirectional LSTM. The combination engine 635 concatenates a character embedding in a forward time direction, a character embedding in a backward time direction, a part-of-speech representation for that word, a word embedding for that word, a gazetteer representation of vector for that word, to generate the combined vector 1005 which is input into the classification engine 640. The combined vector 1005 describes a single word of the caption, e.g., “Florence” from “Florence and the Machine”.

FIG. 11 shows an example architecture 1100 of the classification engine 640, according to some example embodiments. As illustrated, word representations may be input into a bidirectional LSTM and a conditional random field (CRF), where each word in the caption is recursively labeled as belonging to a named entity. The word representations input into architecture 1100 may be the combined vectors (e.g. combined vector 1005 generated from the lexical generator) and may also include a word from the visual word engine 630.

FIG. 12 shows an example visual word engine 630 neural network architecture 1200, according to some example embodiments. The visual word engine 630 comprises three regions including a sequence labelling model (comprising bidirectional LSTM layer 1221 and CRF layer 1222), a visual attention model 1218, and visual modulation gate 1220 layer. At a high-level, given a pair of caption 1204 and image 1202 as input, the Visual Attention Model 1218 extracts regional visual features from the image and computes the weighted sum of the regional visual features as the visual context vector 1224, based on their relatedness with the sentence. The BLSTM-CRF sequence labeling model predicts the label for each word in the caption 1204 based on both the visual context vector 1224 and the textual information of the words. The modulation gate 1220 layer controls the combination of the visual context vector 1224 and the word representations for each word before the CRF layer 1222.

Sequence Labeling Model

The Sequence Labeling Model implements name tagging as a sequence labeling problem. Given a sequence of words: S={s₁, s₂, . . . , s_(n)}, the Sequence Labeling Model aims to predict a sequence of labels: L={l₁, l₂, . . . , l_(n)}, where l_(i)∈L and L is a pre-defined label set. The Sequence Labeling Model comprises bidirectional LSTM layer 1221, which are variants of Recurrent Neural Networks (RNNs) designed to capture long-range dependencies of input. The equations of a LSTM cell are as follows: i _(t)=σ(W _(xi) x _(t) +W _(hi) h _(t)−1+b _(i)) f _(t)=σ(Wxfxt+Whfht−1+b _(f)) c ^(˜) _(t)=tanh(W _(xc) x _(t) +W _(hc) h _(t)−1+b _(c)) c _(t) =f _(t) ⊙c _(t)−1+i _(t) ⊙c ^(˜) _(t) o _(t)=σ(W _(xo) x _(t) +W _(ho) h _(t)−1+b _(o)) h _(t) =o _(t)⊙tanh(c _(t))

where x_(t), c_(t) and h_(t) are the input, memory and hid-den state at time t respectively. W_(xi), W_(hi), W_(xf), W_(hf), W_(xc), W_(hc), W_(xo), and W_(ho) are weight matrices. ⊙ is the element-wise product function and σ is the element-wise sigmoid function. Sequence Labeling Model implements a Bidirectional LSTM because the name tagging task benefits from both of the past (left) and the future (right) contexts. In particular, the right and left context representations are concatenated for each word: h_(t)=[h_(right), h_(left)].

The Sequence Labeling Model generates the character-level representation (“CHAR. EMB.”) for each word using another BLSTM, which is included in architecture 1200 but omitted for clarity. The BLSTM receives character embeddings as input and generates representations combining implicit prefix, suffix and spelling information. The final word representation x_(i) is the concatenation of word embedding e_(i) and character-level representation c_(i). c _(i)=BLSTM_(char)(s _(i)) s _(i) ∈S x _(i)=[e _(i) ,c _(i)]

Further, the Sequence Labeling Model comprises a CRF layer 1222 to consider constraint of the labels in the neighborhood. For example, an I-LOC must follow B-LOC, where LOC refers to the label being a location type and be is “Beginning” and “I” is intermediate”. Thus, as illustrated in FIG. 12, Florence is a B-PER (where PER is for Person type), which is followed by three non-beginning type I-PER labels.

Visual Attention Model

The image 1202 is input into a convolutional neural network (e.g., Residual Network (ResNet) to generate visual vector 1212 comprising visual features for regional areas as well as for the entire image 1202: V _(g)=ResNet_(g)(I) V _(r)=ResNet_(r)(I)

where the global visual vector Vg, which represents the entire image 1202, is the output before the last fully connected layer. The last fully connected layer outputs the probabilities over 1000 classes, according to some example embodiments. The dimension of Vg is 1,024. V_(r) are the visual representations for regional areas and they are extracted from the last convolutional layer of the CNN 1210 (e.g., last layer of ResNet). The dimension of V_(r) is 1,024×7×7, where 7×7 is the number of regions in the image and 1,024 is dimension of the feature vector. Thus, each feature vector of V_(r) corresponds to a 32×32 pixel region of the rescaled input image.

The global visual vector is a reasonable representation of the whole input image 1202 but is improvable. In some cases, only parts of an image are related to the associated caption. The visual attention network is configured to address further improve the visual representation by focusing on regions of the input image that are more likely related or useful in context of the corresponding caption.

In some example embodiments, the attention network 1216 maps a query and a set of key-value pairs to an output 1214. The output 1214 is a weighted sum of the values and the assigned weight for each value is computed by a function of the query and corresponding key. In some example embodiments, the caption 1204 is encoded into a query 1208 (e.g., encoded text) via a LSTM 1206. In particular, the LSTM 1206 encodes the caption 1204 into encoded text, query 1208. The inputs into the LSTM 1206 are the concatenations of word embeddings and character-level word representations. Different from the LSTM model used for Sequence Labeling Model (e.g., “BKD. LSTM”, “FRW. LSTM”), the LSTM 1206 aims to get the semantic information of the caption, and further it the LSTM 1206 is unidirectional: Q=LSTMquery(S)

The attention network 1216 receives the query and the regional visual representations V_(r) as keys and values.

Attention Implementation: Based on experimental results, dot product implementations result in more concentrated attentions and linear projection after summation results in more dispersed attentions. In the context of name tagging, linear projection after summation is implemented because it is beneficial for the model to utilize as many related visual features as possible, and concentrated attentions may make the model bias. For implementation, the text query vector Q and regional visual features V_(r) are projected into the same dimensions: P _(t)=tanh(W _(t) Q) P _(v)=tanh(W _(v) V _(r)) The projected query vector is then summed with each projected regional visual vector respectively: A=P _(t) ⊕P _(v) The weights of the regional visual vectors are: E=softmax(W _(a) A+b _(a)) where Wa is weights matrix. The weighted sum of the regional visual features is: v _(c)=Σα_(i) v _(i) α_(i) ∈E, v _(i) ∈V _(r) The architecture uses v as the visual context vector 1224 to initialize the BLSTM Sequence Labeling Model discussed above. Visual Modulation Gate

In some example embodiments, the visual context vector 1224 is used initialize the LSTM cell, as indicated by the visual context vector 1224 being input into the first cell of “FRW. LSTM”. In some example embodiment, the visual context vector 1224 is not used to initialize the LSTL but incorporated at the word level. Generally, visual features contribute differently when they are used to infer the tags of different words. For example, the architecture 1200 can easily find matched visual patterns from associated images for verbs such as ‘sing’, ‘run’, and ‘play’; and words/phrases such as names of basketball players, artists, and buildings are often well-aligned with objects in images. However, it is difficult to align function words such as ‘the’, ‘of’ and ‘well’ with visual features. Fortunately, most of the challenging cases in name tagging involve nouns and verbs, the disambiguation of which can benefit more from visual features. As such, according to some example embodiments, the visual context vector 1224 is incorporated at word level individually, as indicated by the dotted lines from visual context vector 1224 to respective instances of gates in the modulation gate 1220 layer.

The modulation gate 1220 dynamically controls the combination of visual features and word representation generated by BLSTM at word-level, before feeding them into the CRF layer 1222 for tag prediction. The equations for the implementation of modulation gate 1220 are as follows: β_(v)=σ(W _(v) h _(i) +U _(v) v _(c) +b _(v)) β_(w)=σ(W _(w) h _(i) +U _(w) v _(c) +b _(w)) m=tanh(W _(m) h _(i) +U _(m) v _(c) +b _(m)) w _(m)=β_(w) ·h _(i)+β_(v) ·m

where h_(i) is the word representation generated by BLSTM, v is the computed visual context vector, W_(v), W_(w), W_(m), U_(v), U_(w) and U_(m) are weight matrices, σ is the element-wise sigmoid function, and w_(m) is the modulated word representations input into the CRF layer 1222.

FIG. 13A shows an image 1202 of the multimodal message, according to some example embodiments. The image 1202 depicts a patient 1305 on a hospital bed and a partially out-of-frame guitar player 1310. The corresponding caption 1204 (not depicted in FIG. 13A) is the sentence “Florence and the machine surprise teen with private concert”. Conventionally, the caption 1204 can be difficult to parse because “Florence” could be the name of a person in the image, or refer to something else, such as one term of a band's full name.

FIG. 13B shows an example output of attention network 1216, according to some example embodiments. As illustrated, the attention network 1216 has relevant portions 1315 of the image 1202, thereby minimizing areas not related to the context of the caption. In particular, by using the regional image data (e.g., V_(r), a portion of which depicts a guitar) and the caption 1204, the entity “Florence and the Machine” is identified as a named entity being discussed in the multimodal message.

FIG. 14A shows an example multimodal message 1400, according to some example embodiments. As illustrated, the multimodal message 1400 includes an image of a person on stage 1405 in front of an audience 1410, and a caption 1415 (“JUUUUUUSTIN!!!!<3<3<3” comprising an intentional misspelling of “Justin” and three pictorial heart symbols: “<3”) that has been input by a user of the client device 102. Multimodal message 1400 exam is an example of the multimodal message received or otherwise generated at operation 705 of FIG. 7A. FIG. 14B shows example overlay content 1420 that has been identified by performing the method 700 of FIG. 7A, according to some example embodiments. In particular, for example, the visual named entity recognition system 210 has determined that the caption includes a reference to a named entity, that of the famous singer Justin Bieber. Accordingly, the overlay content 1420 that has been pre-associated with that named entity is retrieved from database 126 and overlaid on the multimodal message 1400 to be stored or otherwise published to a network site as an ephemeral message.

FIG. 15 is a block diagram illustrating an example software architecture 1506, which may be used in conjunction with various hardware architectures herein described. FIG. 15 is a non-limiting example of a software architecture, and it will be appreciated that many other architectures may be implemented to facilitate the functionality described herein. The software architecture 1506 may execute on hardware such as a machine 1150 of FIG. 11 that includes, among other things, processors, memory, and input/output (I/O) components. A representative hardware layer 1552 is illustrated and can represent, for example, the machine 1150 of FIG. 11. The representative hardware layer 1552 includes a processing unit 1554 having associated executable instructions 1504. The executable instructions 1504 represent the executable instructions of the software architecture 1506, including implementation of the methods, components, and so forth described herein. The hardware layer 1552 also includes a memory/storage 1556, which also has the executable instructions 1504. The hardware layer 1552 may also comprise other hardware 1558.

In the example architecture of FIG. 15, the software architecture 1506 may be conceptualized as a stack of layers where each layer provides particular functionality. For example, the software architecture 1506 may include layers such as an operating system 1502, libraries 1520, frameworks/middleware 1518, applications 1516, and a presentation layer 1511. Operationally, the applications 1516 and/or other components within the layers may invoke API calls 1508 through the software stack and receive a response in the form of messages 1512. The layers illustrated are representative in nature and not all software architectures have all layers. For example, some mobile or special-purpose operating systems may not provide a frameworks/middleware 1518, while others may provide such a layer. Other software architectures may include additional or different layers.

The operating system 1502 may manage hardware resources and provide common services. The operating system 1502 may include, for example, a kernel 1522, services 1524, and drivers 1526. The kernel 1522 may act as an abstraction layer between the hardware and the other software layers. For example, the kernel 1522 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. The services 1524 may provide other common services for the other software layers. The drivers 1526 are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 1526 include display drivers, camera drivers, Bluetooth® drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audio drivers, power management drivers, and so forth depending on the hardware configuration.

The libraries 1520 provide a common infrastructure that is used by the applications 1516 and/or other components and/or layers. The libraries 1520 provide functionality that allows other software components to perform tasks in an easier fashion than by interfacing directly with the underlying operating system 1502 functionality (e.g., kernel 1522, services 1524, and/or drivers 1526). The libraries 1520 may include system libraries 1544 (e.g., C standard library) that may provide functions such as memory allocation functions, string manipulation functions, mathematical functions, and the like. In addition, the libraries 1520 may include API libraries 1546 such as media libraries (e.g., libraries to support presentation and manipulation of various media formats such as MPEG4, H.264, MP3, AAC, AMR, JPG, or PNG), graphics libraries (e.g., an OpenGL framework that may be used to render 2D and 3D graphical content on a display), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like. The libraries 1520 may also include a wide variety of other libraries 1548 to provide many other APIs to the applications 1516 and other software components/modules.

The frameworks/middleware 1518 provide a higher-level common infrastructure that may be used by the applications 1516 and/or other software components/modules. For example, the frameworks/middleware 1518 may provide various graphic user interface (GUI) functions, high-level resource management, high-level location services, and so forth. The frameworks/middleware 1518 may provide a broad spectrum of other APIs that may be utilized by the applications 1516 and/or other software components/modules, some of which may be specific to a particular operating system 1502 or platform.

The applications 1516 include built-in applications 1538 and/or third-party applications 1540. Examples of representative built-in applications 1538 may include, but are not limited to, a contacts application, a browser application, a book reader application, a location application, a media application, a messaging application, and/or a game application. The third-party applications 1540 may include an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform, and may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. The third-party applications 1540 may invoke the API calls 1508 provided by the mobile operating system (such as the operating system 1502) to facilitate functionality described herein.

The applications 1516 may use built-in operating system functions (e.g., kernel 1522, services 1524, and/or drivers 1526), libraries 1520, and frameworks/middleware 1518 to create user interfaces to interact with users of the system. Alternatively, or additionally, in some systems, interactions with a user may occur through a presentation layer, such as the presentation layer 1511. In these systems, the application/component “logic” can be separated from the aspects of the application/component that interact with a user.

FIG. 16 is a block diagram illustrating components of a machine 1600, according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 16 shows a diagrammatic representation of the machine 1600 in the example form of a computer system, within which instructions 1616 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine 1600 to perform any one or more of the methodologies discussed herein may be executed. As such, the instructions 1616 may be used to implement modules or components described herein. The instructions 1616 transform the general, non-programmed machine 1600 into a particular machine 1600 programmed to carry out the described and illustrated functions in the manner described. In alternative embodiments, the machine 1600 operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1600 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1600 may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smartphone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions 1616, sequentially or otherwise, that specify actions to be taken by the machine 1600. Further, while only a single machine 1600 is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions 1616 to perform any one or more of the methodologies discussed herein.

The machine 1600 may include processors 1610, memory/storage 1630, and I/O components 1650, which may be configured to communicate with each other such as via a bus 1602. The memory/storage 1630 may include a memory 1632, such as a main memory, or other memory storage, and a storage unit 1636, both accessible to the processors 1610 such as via the bus 1602. The storage unit 1636 and memory 1632 store the instructions 1616 embodying any one or more of the methodologies or functions described herein. The instructions 1616 may also reside, completely or partially, within the memory 1632, within the storage unit 1636, within at least one of the processors 1610 (e.g., within the processor cache memory accessible to processor units 1612 or 1614), or any suitable combination thereof, during execution thereof by the machine 1600. Accordingly, the memory 1632, the storage unit 1636, and the memory of the processors 1610 are examples of machine-readable media.

The I/O components 1650 may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components 1650 that are included in a particular machine 1600 will depend on the type of machine. For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components 1650 may include many other components that are not shown in FIG. 16. The I/O components 1650 are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. In various example embodiments, the I/O components 1650 may include output components 1652 and input components 1654. The output components 1652 may include visual components (e.g., a display such as a plasma display panel (PDP), a light-emitting diode (LED) display, a liquid-crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth. The input components 1654 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instruments), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like.

In further example embodiments, the I/O components 1650 may include biometric components 1656, motion components 1658, environment components 1660, or position components 1662 among a wide array of other components. For example, the biometric components 1656 may include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram-based identification), and the like. The motion components 1658 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environment components 1660 may include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas sensors to detect concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components 1662 may include location sensor components (e.g., a GPS receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies. The I/O components 1650 may include communication components 1664 operable to couple the machine 1600 to a network 1680 or devices 1670 via a coupling 1682 and a coupling 1672, respectively. For example, the communication components 1664 may include a network interface component or other suitable device to interface with the network 1680. In further examples, the communication components 1664 may include wired communication components, wireless communication components, cellular communication components, near field communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices 1670 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).

Moreover, the communication components 1664 may detect identifiers or include components operable to detect identifiers. For example, the communication components 1664 may include radio frequency identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional barcodes such as Universal Product Code (UPC) barcode, multi-dimensional barcodes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF418, Ultra Code, UCC RSS-2D barcode, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components 1664, such as location via Internet Protocol (IP) geolocation, location via Wi-Fi® signal triangulation, location via detecting an NFC beacon signal that may indicate a particular location, and so forth.

Glossary

“CARRIER SIGNAL” in this context refers to any intangible medium that is capable of storing, encoding, or carrying instructions 1616 for execution by the machine 1600, and includes digital or analog communications signals or other intangible media to facilitate communication of such instructions 1616. Instructions 1616 may be transmitted or received over the network 1680 using a transmission medium via a network interface device and using any one of a number of well-known transfer protocols.

“CLIENT DEVICE” in this context refers to any machine 1600 that interfaces to a communications network 1680 to obtain resources from one or more server systems or other client devices 102. A client device 102 may be, but is not limited to, a mobile phone, desktop computer, laptop, PDA, smartphone, tablet, ultrabook, netbook, multi-processor system, microprocessor-based or programmable consumer electronics system, game console, set-top box, or any other communication device that a user may use to access a network 1680.

“COMMUNICATIONS NETWORK” in this context refers to one or more portions of a network 1680 that may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, a network or a portion of a network 1680 may include a wireless or cellular network and the coupling may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or another type of cellular or wireless coupling. In this example, the coupling may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High-Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long-Term Evolution (LTE) standard, others defined by various standard-setting organizations, other long-range protocols, or other data transfer technology.

“EPHEMERAL MESSAGE” in this context refers to a message 400 that is accessible for a time-limited duration. An ephemeral message 502 may be a text, an image, a video, and the like. The access time for the ephemeral message 502 may be set by the message sender. Alternatively, the access time may be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message 400 is transitory.

“MACHINE-READABLE MEDIUM” in this context refers to a component, a device, or other tangible media able to store instructions 1616 and data temporarily or permanently and may include, but is not limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage (e.g., erasable programmable read-only memory (EPROM)), and/or any suitable combination thereof. The term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store instructions 1616. The term “machine-readable medium” shall also be taken to include any medium, or combination of multiple media, that is capable of storing instructions 1616 (e.g., code) for execution by a machine 1600, such that the instructions 1616, when executed by one or more processors 1610 of the machine 1600, cause the machine 1600 to perform any one or more of the methodologies described herein. Accordingly, a “machine-readable medium” refers to a single storage apparatus or device, as well as “cloud-based” storage systems or storage networks that include multiple storage apparatus or devices. The term “machine-readable medium” excludes signals per se.

“COMPONENT” in this context refers to a device, a physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may be combined via their interfaces with other components to carry out a machine process. A component may be a packaged functional hardware unit designed for use with other components and a part of a program that usually performs a particular function of related functions. Components may constitute either software components (e.g., code embodied on a machine-readable medium) or hardware components. A “hardware component” is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware components of a computer system (e.g., a processor 1612 or a group of processors 1610) may be configured by software (e.g., an application or application portion) as a hardware component that operates to perform certain operations as described herein. A hardware component may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic that is permanently configured to perform certain operations. A hardware component may be a special-purpose processor, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). A hardware component may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware components become specific machines (or specific components of a machine 1600) uniquely tailored to perform the configured functions and are no longer general-purpose processors 1610. It will be appreciated that the decision to implement a hardware component mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations. Accordingly, the phrase “hardware component” (or “hardware-implemented component”) should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein.

Considering embodiments in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one instance in time. For example, where a hardware component comprises a general-purpose processor 1612 configured by software to become a special-purpose processor, the general-purpose processor 1612 may be configured as respectively different special-purpose processors (e.g., comprising different hardware components) at different times. Software accordingly configures a particular processor 1612 or processors 1610, for example, to constitute a particular hardware component at one instance of time and to constitute a different hardware component at a different instance of time.

Hardware components can provide information to, and receive information from, other hardware components. Accordingly, the described hardware components may be regarded as being communicatively coupled. Where multiple hardware components exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware components. In embodiments in which multiple hardware components are configured or instantiated at different times, communications between or among such hardware components may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware components have access. For example, one hardware component may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware component may then, at a later time, access the memory device to retrieve and process the stored output. Hardware components may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).

The various operations of example methods described herein may be performed, at least partially, by one or more processors 1610 that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors 1610 may constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented component” refers to a hardware component implemented using one or more processors 1610. Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor 1612 or processors 1610 being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors 1610 or processor-implemented components. Moreover, the one or more processors 1610 may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines 1600 including processors 1610), with these operations being accessible via a network 1680 (e.g., the Internet) and via one or more appropriate interfaces (e.g., an API). The performance of certain of the operations may be distributed among the processors 1610, not only residing within a single machine 1600, but deployed across a number of machines 1600. In some example embodiments, the processors 1610 or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors 1610 or processor-implemented components may be distributed across a number of geographic locations.

“PROCESSOR” in this context refers to any circuit or virtual circuit (a physical circuit emulated by logic executing on an actual processor 1612) that manipulates data values according to control signals (e.g., “commands,” “op codes,” “machine code,” etc.) and which produces corresponding output signals that are applied to operate a machine 1600. A processor may, for example, be a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an ASIC, a radio-frequency integrated circuit (RFIC), or any combination thereof. A processor 1610 may further be a multi-core processor 1610 having two or more independent processors 1612, 1614 (sometimes referred to as “cores”) that may execute instructions 1616 contemporaneously.

“TIMESTAMP” in this context refers to a sequence of characters or encoded information identifying when a certain event occurred, for example giving date and time of day, sometimes accurate to a small fraction of a second. 

What is claimed is:
 1. A method comprising: identifying, using one or more processors of a machine, a multimodal message that includes an image and a caption comprising words; generating, using an attention neural network, a visual context vector from the caption and the image, the visual context vector indicating relevant portions of the caption in relation to objects depicted in the image; generating, using an entity recognition neural network, indications that one or more words of the caption correspond to a named entity; storing the one or more words as the named entity of the multimodal message; and generating encoded text from the caption using a recurrent neural network, wherein the attention neural network generates the visual context vector at least in part from the encoded text.
 2. The method of claim 1, further comprising: selecting one or more items of content using the named entity; and generating a modified multimodal message comprising the image, the caption, and the one or more items of content.
 3. The method of claim 1, further comprising: generating, using a convolutional neural network, one or more image vectors from the image, wherein the attention neural network generates the visual context vector from the encoded text and the one or more image vectors.
 4. The method of claim 3, wherein the image vectors comprise a global vector corresponding to the image and regional vectors corresponding to regions of the image.
 5. The method of claim 1, wherein a word of the caption comprises at least one or more of: individual characters, symbols, a sequence of characters.
 6. The method of claim 5, wherein the entity recognition neural network comprises a bi-directional neural network and a conditional random field layer.
 7. The method of claim 1, further comprising: initializing the entity recognition neural network using the visual context vector as an initial data input item.
 8. The method of claim 1, further comprising: integrating, using a modulation layer, the visual context vector into the entity recognition neural network for each word in the caption.
 9. The method of claim 1, wherein the entity recognition neural network and the attention neural network are trained end-to-end.
 10. A system comprising: one or more processors of a machine; and a memory storing instructions that, when executed by the one or more processors, cause the machine to perform operations comprising: identifying, using one or more processors of a machine, a multimodal message that includes an image and a caption comprising words; generating, using an attention neural network, a visual context vector from the caption and the image, the visual context vector indicating relevant portions of the caption in relation to objects depicted in the image; generating, using an entity recognition neural network, indications that one or more words of the caption correspond to a named entity; and storing the one or more words as the named entity of the multimodal message; and generating encoded text from the caption using a recurrent neural network, wherein the attention neural network generates the visual context vector at least in part from the encoded text.
 11. The system of claim 10, the operations further comprising: selecting one or more items of content using the named entity; generating a modified multimodal message comprising the image, the caption, and the one or more items of content.
 12. The system of claim 10, the operations further comprising: generating, using a convolutional neural network, one or more image vectors from the image, wherein the attention neural network generates the visual context vector from the encoded text and the one or more image vectors.
 13. The system of claim 12, wherein the image vectors comprise a global vector corresponding to the image and regional vectors corresponding to regions of the image.
 14. The system of claim 10, wherein a word of the caption comprises at least one or more of: individual characters, symbols, a sequence of characters.
 15. The system of claim 10, wherein the entity recognition neural network comprises a bi-directional neural network and a conditional random field layer.
 16. The system of claim 10, further comprising: initializing the entity recognition neural network using the visual context vector as an initial data input item.
 17. The system of claim 10, further comprising: integrating, using a modulation layer, the visual context vector into the entity recognition level for each word in the caption.
 18. A machine-readable storage device embodying instructions that, when executed by a machine, cause the machine to perform operations comprising: identifying, using one or more processors of a machine, a multimodal message that includes an image and a caption comprising words; generating, using an attention neural network, a visual context vector from the caption and the image, the visual context vector indicating relevant portions of the caption in relation to objects depicted in the image; generating, using an entity recognition neural network, indications that one or more words of the caption correspond to a named entity; storing the one or more words as the named entity of the multimodal message; and generating encoded text from the caption using a recurrent neural network, wherein the attention neural network generates the visual context vector at least in part from the encoded text. 